Part 5: .44444444444
Doesn't that J person die or something in the anime? Making it the first death ever? (after like 500 episodes)
Also HOLY FUCK YOU GUYS IT'S AN UPDATE.
update 05: .44444444444
Why yes hello, last time blocky decided to go rouge and attack the game by having game breaking moves he shouldn't have. Quite frankly I don't condone such behavior, but I don't think there will be too much harm in keeping him for now.
![](1-capture_10042010_104115.png)
After the sabotage I decided to reset the game and fight Gary again without taking out blocky, as you can see the effects have turned out to be satisfactory.
![](2-capture_10042010_104118.png)
![](3-capture_10042010_104127.png)
A learns a new move, and as a result cooltrainer is gone and we have a nice coherent moveset now! I hear guillotine is useful.
![](4-capture_10042010_104508.png)
To our convenience A also learns a TM move one level after learning gust, which was properly replaced (although looking back I probably should have taken away Razor wind, ah well). Now, I have recently discovered that bulbapedia actually has a pretty good in-depth article about various glitch moves and their damage and accuracy, which means I can be a bit more informative about them, in this case...
TM 08
Type: Normal
Power: 30
Accuracy: 17%
PP: 20
![](5-capture_10042010_104622.png)
TM 08 is a really lame move. It has the same characteristics as Hitmonlee's high jump kick except no where near as good. As you can see it has a pitifully low attack and it's normal type to boot. It misses a lot, and whenever you miss you get hurt, I would definately suggest against relying on this move in any way.
![](6-capture_10042010_104615.png)
It's got a really funky typing going for it though, this is A's unique glitch typing. I am quite fond of it.
![](7-capture_16042010_111700.png)
Those were the last of the leftover screenshots from last update that I forgot to put in. With that out of the way it is time to announce what we're gonna be doing for the next couple of updates. If you can kindly divert your attention away from Red who has become fucked beyond fixing, please take a gander at the badges. We got about 3 more left to go before we can utilize the glitches that involve surf and fly. Until then it's gonna be more sharking with little in-game glitching, and then we can finally duplicate rare candies in joy and glee as the grinding in Cerulean Cave can finally be over. Seriously these pokegods need an ASS load of more exp than normal pokes to level up, having to grind in Cerulean Cave is ridiculous. I'm mainly pointing this out to show that I'm not just ignoring our old pokegods as we get news ones, they will all become properly leveled in due time when I can do by just mashing the "A" button a bunch.
Now it's time for our next pokegod, this one, in my opinion, is where we start getting into some serious shit.
![](8-capture_16042010_112434.png)
Meet .4, also meet Loaded State 1 because I am terrible at timing the screenshots. .4 is quite honestly, the game fucker. If you encounter and catch .4, it will make your game go on its knees and have the game suck its glitch dick. When it is done, .4 will grab a hammer and keep slamming on the game's head until it is quite near death, and then, only then, if .4 feels merciful enough, it will keep the game going, only to have it probably die within a couple of minutes.
tl;dr .4 will fuck up your game if you're not careful
![](9-capture_16042010_112526.png)
So of course I catch it, it's not like save states get affected by in-game glitches... Right? Notice how .4 has somewhat low health, I didn't HAVE to weaken it, but I wanted to show this off, saying that it took A, a level 15 pokemon, 3 turns to wittle down the health of a level 3 pokemon. .4 usually tends to have an upper hand in defense, and I will explain why I say "usually".
![](10-capture_16042010_112530.png)
Lucky for me, I'm not forced to look at .4's pokedex since I've already seen magneton, which are somewhat common in the Cerulean Cave. It seems that you don't actually have to catch the pokemon with a similar capture flag of a glitch pokemon, simply seeing them is good enough, who knew?
![](11-capture_16042010_112539.png)
![](12-capture_16042010_112543.png)
Here are .4's stats and moves. Apparently his first type is "Pokemaniac". I have no idea why this is, it's not related to the glitch move explanation I gave last update, it's just a thing. .4 is also pretty weird when it comes to moves, you may notice that I caught .4 at a very low level, which was kinda going against what I had going on with the other pokegods. That is, I caught them as I got into higher level grass patches that led to the next gyms. Well interestingly enough if you catch .4 at a level more than... let's say 5, somewhere around that area. .4 gets those fucked up glitch moves that cause the game to go wack (by the way I've found explanations for those! Hold on tight for the upcoming explanation). When you catch .4 at a low level like I did, his move set is still... Weird.
Hopefully I don't have to point out that .4 has two of the same move, agility. He also has TM29, and a nameless move at the top. That nameless move right there, that is one of the big things that makes .4 very dangerous. That move is similar to the sharked moves that I made fatty use, and according to bulbapedia, it is defined as a "SUPERGLITCH" move.
What is Super Glitch you may ask? Well, it seems that Super Glitch defines a large amount of unstable glitch moves that reside in the Gameboy's hexidecimal slot AC to C3 in the pokemon red and blue American moves. They look weird, usually have no name and some strange typing, and most - if not all - cause a similar occurence called the "TM TRAINER" effect. This, as we've seen, changes the player's name to TM TRAINER that is followed by unreadable glitch dialouge. Then, as we've seen the health bars go crazy and some burn/poison/frozen(?) damage causes the pokemon to slowly lose health and the health bar loop several times before finally fainting. What happens after is pretty big fair game. Why does this happen you may ask? Well it seems that these attacks will scramble around the Game's RAM, which (usually) causes the game to freeze after the completion of the super glitch move. To be honest, using super glitch itself will not really erase your game, but if it is used AGAINST you, then you're probably in trouble.
Quite a lot of words, I guess I should put in .4's glitch dex while we're at it.
.4
AKA: u.4, "uyon"
Pokemon #234
Type 1/Pokemaniac
Hex Value: C2
Starting Moves: Nameless Glitch Move, Agility, TM28, Agility
Yellow Equivalent: pPkMnp
Base and Max Stats
HP: 179, Atk: 96, Def: 209, Spd: 96, Spl: 21
HP: 561, Atk: 290, Def: 516, Spd: 290, Spl: 140
Learned Moves: TM05 (Lv. 9), Surf (Lv. 19), TM09 (Lv.30), TM34 (Lv. 44), Wing Attack (Lv. 55), Cut (Lv. 61), Karate Chop (Lv. 62), Flash (Lv. 70), TM11 (Lv. 94), Glitch Move (Lv. 97)
Learned Moves over level 100: TM05 (Lv. 109), Guillotine (Lv. 170), TM08 (Lv. 183), TM34 (Lv. 184), <freezes game when learned> (Lv. 195), Minimize (Lv. 205), TM50 (Lv. 208), TM01 (Lv. 225), <Freezes game when learned> (Lv. 234), <Freezes game when learned> (Lv. 240), TM24 (Lv. 241), TM50 (Lv. 245), TM29 (Lv. 255)
TM Moves: Strength, Flash, Razor Wind, Toxic, Horn Drill, Take Down, Hyper Beam, Counter, Solar Beam, Dragon Rage, Thunder, Mimic, Bide, Fire Blast, Swift, Dream Eater, Sky Attack, Rest, Thunder Wave, Psywave, Explosion, Substitute
Encounter Flag: unknown
Capture Flag: Magneton encounter
.4's first attack has some unusual effects, sometimes it will have the Super glitch effect. Other times it will do some incomprehensible things as turning enemy pokemon into Vulpix. Sometimes the move will have "No effect!" and it can also make .4 take a nap. Like other glitches, catching .4 will make your in game battle sprites all scrambled. .4 is unique in that it naturally learns 3 of 5 HM moves (By which I mean it actually learns "Surf", not the move that is named after the HM). When .4 learns some of its later moves, it will cause weird effects giving you extra pokemon that will be poisoned and faint. Healing at the pokemon center or by your mom will cause strange effects. It is not recommended to actually catch .4 as it has been known to corrupt save files.
If you've read through that and sound interested, guess what? We're gonna see how it all goes down, let's get started! I guess I should show off how .4 looks in battle first if you use him... "Normally".
![](13-capture_16042010_112619.png)
Here's how .4's attacks look like on a good day. The top glitch attack is of the flying type and will keep switching in name wise. In this case it has my rival's name, but it can quickly change to look like different things, usually just glitch blobs. The TM move is just the same as always, having the same typing as the last trainer you fought or Cooltrainer.
TM 28
Type: Bug (huh)
Attack: 85 (probably the best bug move in the game)
accuracy: 46% (Better than what we've usually seen)
PP: 30
Overall TM 28 seems to be pretty solid compared to the other TM moves we've seen so far.
![](14-capture_16042010_112632.png)
It has an explosion animation and then does that animation where you have a bunch of "POW" look sprites going across the opponent. Using it is completely safe, and the only downside is that it will probably make .4's sprite dissappear. Actually I should point out, .4 has two sprites! One is the one we see now, the other is like some weird floating thing in the air, very tiny. As a result if you catch this other form and send it out to battle it will have the smallest backsprite of any pokemon in any of the games. For some reason I couldn't encounter it. Also .4's cry is that of the little "Nudge" sound pokeballs make when you're trying to catch something and it shakes.
![](15-capture_16042010_112650.png)
Against certain pokemon like rattata (and pretty much a lot of the early wild pokemon), .4's mystery move will have "no effect" on the opposing pokemon. Making it about as useful as Magikarp's splash. That's pretty much all there is to show from here, let's see what happens if we can make .4 learn his next move, TM05, at level 9.
![](16-capture_16042010_113451.png)
![](17-capture_16042010_113459.png)
Pretty normal so far, I tried to make .4 forget one of his two agilities because seriously he doesn't even have use for one... But then of course, something happens.
![](18-capture_16042010_113502.png)
.4 doesn't know waterfall.
![](19-capture_16042010_113512.png)
![](20-capture_16042010_113516.png)
And this time...
I caught it on video
![](21-capture_16042010_113604.png)
![](22-capture_16042010_113619.png)
Unfortunately this chain of evolutions did not last nearly as long as last time, however I have good news. Right after all this was over, I made a separate save state for this, I know what's up, and I'm ready to abuse what happens post-game. In case you're confused let me explain, before .4 evolved I made a save state, this save state is what we're gonna use to progress through the game as normal as we can. The save state I made after .4's level up and learning a move, that's a separate save state that we'll be using to play around with for now and revisit later.
![](23-capture_16042010_113642.png)
There are some rules that I - and hopefully you - have learned when traversing the apocalypse. One important rule is that the pokemon screen should never be viewed, EVER. Doing so will introduce a white screen that one can not escape out of, leaving Red to eternal madness. As you can see, after the evolution chain we have gained some pokemon (I only had 5 before) and it appears half have been status affected.
![](24-capture_16042010_113650.png)
.4 has transformed from a somewhat harmless level 8 glitch into a monster, you can't see it now, but he is actually over 200 levels. As a matter of fact I don't even know why I have this screenshot because it's the only one I have of this fight. I have a better showing off of how .4 is at this stage anyway, let this thing just be an omen.
![](25-capture_16042010_113726.png)
The start screen has been morphed into a bastardized version of its former self. Check out my name, it's switched from "Met" to "TM TRAINER", hence how the "TM TRAINER" effect got its name. As I said before we can't view the pokemon, so let's see how our trainer card is fairing.
![](26-capture_16042010_113732.png)
Not too well. Also my name is now PCPoke, MAKE UP YOUR MIND GAME!
![:argh:](../Smilies/emot-argh.gif)
![](27-capture_16042010_113830.png)
Nameless creatures are fainting, and my screen keeps flashing involving I still have poison, it's kind of annoying. A quick trip to the pokemon center should be able to fix it.
![](28-capture_16042010_113916.png)
Huh, everything seems to be going well but... What's that stuff on the top?
![](29-capture_16042010_113924.png)
Uh-oh
![](30-capture_16042010_113947.png)
Gee, thanks Nurse. Then the emulator crashes when you're done talking to her. That's right, not the game, but the emulator itself has to lock down because it can't comprehend what's going on. Let me explain what happened, you know how when you get your pokemon healed at the center, and pokeballs pop up making a low "Boop" noise? Well, the "Boop" noises didn't stop after the 6 pokeballs, and for each Boop noise the screen got more and more glitched. You can't tell from the screenshots, but the booping went on for nearly a minute. This means, not only do I have more than 6 pokemon, I have a FUCKTON of pokemon. How can we view them though? We can't look at the pokemon menu screen, well, there's an alternative, Bill's PC!
CRASHMAN PROVES ME WRONG
quote:
Actually, you have zero Pokemon. There's a value in RAM which stores how many Pokemon you have in your party for things like Pokemon Centres; when adding Pokemon to the machine it executes a "subtract one, compare with 0, if not equal do it again" loop. When that value is zero the first subtraction circles over to 255, so it ends up drawing 256 Pokeballs (most of which end up being glitchy crap at the top of the screen due to overrunning the end of an array). It's the same bug that causes the split screen in Pac-Man.
Bill's PC works differently, so you can actually fiddle with arbitrary bits of system memory (which is how that incomprehensible TAS of Pocket Monsters Red/Green does its thing).
![](31-capture_16042010_114033.png)
![](32-capture_16042010_114036.png)
Unfortunately even the PC seems to have been affected by .4's superglitch.
![](33-capture_16042010_114043.png)
![](34-capture_16042010_114052.png)
I go to see what happens if I try to deposit my pokemon, the results are... Interesting. As you can see .4 is a whopping level of 234, but the fun doesn't end there.
![](35-capture_16042010_114056.png)
![](36-capture_16042010_114058.png)
![](37-capture_16042010_114102.png)
Glitched pokemon. As far as your human eye can see, it is nothing but glitches. Some of them ridiculously powerful at levels beyond game comprehension, some of them at a measly level 0.
![](38-capture_16042010_114152.png)
![](39-capture_16042010_114155.png)
And by measly I mean measly. 0 across the board, except for three things. They are part bird type, which is a type that can't be viewed under normal means. It is also apparently Missingno.! Everyone's favorite glitch, hopefully we'll get to him soon enough. These guys can apparently level up too, but there's no way we can access them since that would require looking at the pokemon screen.
![](40-capture_16042010_114206.png)
Scanning random glitches, I found some interesting things. Mainly this level 140 spearow with a 60 in every stat, not really impressive mind you. It's OT (Original Trainer) is also Mew...
![](41-capture_16042010_114346.png)
There's this guy who seems to have an insane attack and defense, but straight up 0's in speed and special. His OT is DY, the elusive DY appears again! What could it be? Maybe it's the "DY" at the end of Durpady?
![](42-capture_16042010_114520.png)
![](43-capture_16042010_114522.png)
Finally, here is the all new .4. It now knows moves it never had before, and has stats of the most insane ranges. It has become, quite literally, a pokegod (even though it's number has reverted back to 000 which is lame).
Looking at some other things, if you keep going down into the deposit menu you'll just end up in an endless wave of level 0 pokemon. Most of the pokemon make your game freeze when you view their stats so welp, the computer works fine other than the deposit menu here.
![](44-capture_16042010_114925.png)
Despite .4's godly stats he is as worthless as all unholy fuck. Every attack, no matter what you choose, will act as rest. .4 will sleep, and that is all he will be able to do. Do what I tell you, unholy abomination!
There's more to do that I know of when the game is at this state, but I think we're done for now. We're gonna go back to our playable save and finally go attack the 4th gym to go on with our lives.
![](45-capture_16042010_131115.png)
From Cerulean we reach Lavender town through the dark cave or whatever it's called. The place where you need flash. Nothing interesting happened along the way, Mew kind steamrolled everything. Ironically, the lavender town track is one of my favorites despite it scaring the crap out of little me back in the day. It's nice and moody.
Speaking of moody and depressing things:
![](46-capture_16042010_131239.png)
Fighting Blue here? There's supposedly a whole reason behind it. Basically when you fought Blue at the SS Anne he had a raticate, when you fight him here he doesn't have a raticate anymore, supposedly it died and he was there to pray for it. The FR/LG translation does a lot better job in expressing it because Blue actually seems a bit peeved off in that version, here he's still all cocky and 1 dimensional. Whatever Mew kicked his ass easy.
![](47-capture_16042010_131449.png)
Oh man, this ghost scared the shit out of me when I was a kid. Unfortunately I'm really disappointed in it right now. It seems that not even glitches are enough to somehow fight this thing. Even A, a pokegod, is to scared to fight it. If you have an "Encounter only this pokemon" cheat on the ghost will still be the only thing that appears. Someone mentioned using a pokedoll on it, yeah that didn't do shit, I just escaped from the battle like normal. God, this ghost was so disappointing, it didn't do anything, I'm so mad at this ghost.
![](48-capture_16042010_133000.png)
As a matter of fact I was so peeved by the ghost that I just left it there. Let it haunt for all I care, I'm gonna leave it alone. If you guys know of something fun to do with the ghost, tell me. Cause I can't think of anything. For now...
![](49-capture_16042010_133023.png)
Wait, since when did Erika know telepathy? I thought that was Sabrina?
![](50-capture_16042010_133037.png)
Remember when I said A's guillotine was really good? This is a good representation as to why. Mother fucking A not only went first for Erika's first 2 pokemon, but it one-hit Ko'd BOTH of them. I was getting excited to defeat Erika in three turns, but A missed on vileplume which proceeded to giga-drain the fuck out of him. (Draining a pokegod can't be healthy)
![](51-capture_16042010_133123.png)
![](52-capture_16042010_133135.png)
Mew finishes the job (if you're wondering it got poisoned cause I got stupid and walked into an earlier beauty's range who then poisoned it with bellsprout or something) and I get my rainbow badge. Unfortunately it's neither fly nor surf usage, but strength.
Well, that should be it for this update, but I wanted to put in a particular in game glitch that's very easy to do and very dear to my heart.
![](53-capture_16042010_133756.png)
This house is the most southern-east one of Cerulean City. It is a hotel, for people. Normally this makes it pretty much one of the most useless areas in the game since NO ONE there gives your anything or says anything interesting. However, that is all fixed by what I think may have been a simple overlook.
![](54-capture_16042010_133819.png)
There is an INVISIBLE PC HERE. How cool is that? It's pretty much at the same spot where a normal PC at a pokemon center would be too. As a matter of fact this "Hotel" pretty much has the exact same geography as a pokemon center. Call it a hunch, but I think this place was supposed to have much more in it and gamefreak didn't have the time to include it, if only we knew...
![](55-capture_16042010_133846.png)
While we're here, I might as well show off a cloning glitch that a generous goon has informed of me. It's a finicky process, and quite honestly I myself wouldn't recommend it since it involves turning the game off when it's saving which usually doesn't lead to anything good. Hey, if you're good at timing though...
The first thing to do is switch to an empty box, and put the pokemon you want cloned in it, we'll use Mew for this.
![](56-capture_16042010_133853.png)
![](57-capture_16042010_133905.png)
Next we have to switch to an empty box. Now before Gen 3 the game had to save when switching boxes (which was, let me tell you from memory, the most goddamn annoying thing if you had a lot of pokemon). When you click on a box to switch, the game begins to save, right when you press the A button to switch the box, reset your game.
![](58-capture_16042010_133934.png)
![](59-capture_16042010_134008.png)
If you did it right, you have the pokemon you wanted to clone in your party, and its clone in the box you put it in! Congrats, you now have 2 of your original pokemon! I have to say though, this trick was really hard to do. It is probably because I was doing it on an emulator, but I was only really able to do this successfully once, with Mew, I tried doing it with pokegods, but I just couldn't get it to work. Perhaps it's a lot easier on the original gameboy?
That's it for now everyone, next time... ZZZZAAAZZZAAZAZAZAZZZAZZZ (yes that is an actual thing)
EDIT:
You may be wondering how the game can keep on going despite some of the crazy stuff that's happened. Well, local coding wizard NRVNQSR has the answers!
quote:
Memory protection is a system that prevents programs from reading or writing bits of memory that they shouldn't, either because they're not allowed to or because the memory doesn't even exist. If a program tries, it will crash. When a modern game crashes, 95% of the time it's memory protection that strikes the killing blow: As the game gets more and more confused, it's more and more likely that it will ask a question it shouldn't and the system will smack it down. It might be called an "access violation" or a "segmentation fault" or a dozen other names, but they're all the same thing.
All modern PCs and almost all modern consoles have some form of memory protection. But as you go further back in time, especially on smaller portable consoles, it gets rarer and more limited; memory protection isn't free, and processing power was at a premium.
So when a gameboy game asks to read a bit of memory that's slightly wrong? Sure, go ahead. When, based on that, it tries to write to a chunk of memory that's miles from where it should be, smack in the middle of a Pidgey's sprite data? No problem. It can just keep going round in circles, getting more and more confused. It's all crazy, but without a memory manager keeping an eye on things none of it is actually going to make the game crash. As long as the game can find its way back out to some code that works again, it can carry on as if nothing had happened.
When a game on an old system like this actually crashes, it's usually either because the hardware has been asked to do something completely impossible (dividing by zero is a classic, though some systems will try anyway), because the program has gone into an infinite loop, or because the programmer has specifically told it to die ("if the player encounters a Pokemon that shouldn't exist, then crash").
Many games use that last one a lot; better to have the game crash than let it continue in a messed up form, especially if there's a risk of it messing up their saves. Obviously Pokemon isn't one of these games.